Ambiguity & initiative
Leadership without title
Product thinking
AI / edtech
Delivery under pressure
Cross-functional
S — Situation
We were building Teacher Hub — an experimental AI feature for standards-based analytics and AI-generated lesson plans. The PM had a shifting, unclear roadmap with no concrete spec. Mid-project, the pipeline engineer who had been leading the technical work left the company. We also had no clear design direction. The project was at risk of stalling entirely, with a hard deadline tied to a commitment to 2 school districts.
T — Task
I stepped up to lead without being asked. The PM's role was high-level — they'd only give directional feedback. That meant I was responsible for figuring out both what to build and how to build it, within a fixed 2-month window despite a missing technical lead and open technical challenges.
A — Action
At first, I did a market audit. Most teacher tools either had no student data — making their AI-generated lesson plans generic and not grounded in reality — or had data but could only do basic reporting, with no connection to academic standards. Neither was actually useful to teachers.
I saw that we had a unique advantage: real student performance data plus the ability to map it to curriculum standards. So I defined a differentiated approach — deep analysis combining actual classroom performance data with standards alignment, feeding into AI-generated lesson plans targeted to specific student gaps.
I used this research to write the product spec to define what we'd ship.
Only then did I move to implementation. I picked up the pipeline work left by the departed engineer, worked through the technical blockers, and kept the team on track across the 2 months.
R — Result
Delivered on time to both school districts — 100+ teachers in total. The feedback was strong enough that both districts extended their contracts. What made the difference was that we weren't giving teachers another generic AI tool — we were giving them insights grounded in their own students' actual performance, tied to the standards they're accountable to.
2 months, on time
100+ teachers
contracts extended
2 districts
90-second version — ready to say out loud
"We were building an AI feature called Teacher Hub — standards-based analytics and lesson plan generation for teachers. Midway through, our lead pipeline engineer left the company, the PM had a shifting roadmap with no real spec, and the project was at risk of going nowhere. I stepped up to lead it, even though it wasn't formally my responsibility.
Before I touched the code, I did a market audit. What I found was that most teacher tools either had no student data — so their AI outputs were generic and not grounded in anything real — or they had data but could only do basic charts with no connection to academic standards. Neither was actually useful. What we had that no one else did was real student performance data plus the ability to link it to curriculum standards.
So I defined a differentiated approach: give teachers deep analysis combining their students' actual performance with standards alignment, then use that to generate AI lesson plans targeted to real gaps. I used this to realign the PM and designer around a concrete scope, then built it — picking up the pipeline work left behind, and working through the technical challenges.
We shipped on time, 2 months after I took over.` The feature went out to 2 school districts, over 100 teachers. The feedback was strong enough that both districts extended their contracts."
Click to get coaching on pacing and delivery
Covers: "Tell me about ambiguity" · "Leadership without authority" · "Most impactful project" · "How do you handle unclear requirements" · "Tell me about a time you took initiative" · "Proudest technical work"
The differentiator insight is the strongest moment in this story — "most tools have no data, or data but no standards connection — we combined both." Say it clearly and slowly. Interviewers remember the product insight as much as the engineering. Don't rush past it.
Angle variations — click to get a version tuned for that question
"Tell me about a time you dealt with ambiguity"
Lead with: no roadmap, no owner, departed engineer
Make the research process your answer to the ambiguity
"Influencing product direction"
Lead with: PM had no clear vision — I redefined it
Center the market research and the new spec you wrote
"Delivery under pressure / at risk"
Lead with: engineer departed, deadline was fixed
Emphasize picking up the pipeline work and the technical challenges
"Most impactful / proudest project"
Lead with: the customer outcome and what teachers can do now
Lead with the contracts extended, then reveal the chaos it took to get there